Skip to content

fix: use personal namespace for MCP registry publishing#40

Merged
jeff-atriumn merged 1 commit intomainfrom
fix/mcp-registry-name
Feb 27, 2026
Merged

fix: use personal namespace for MCP registry publishing#40
jeff-atriumn merged 1 commit intomainfrom
fix/mcp-registry-name

Conversation

@jeff-atriumn
Copy link
Member

Change Summary

Switch MCP registry name from io.github.atriumn/tokencost-dev to io.github.jeff-atriumn/tokencost-dev. The registry's org membership verification isn't resolving for the atriumn org despite public membership.

Risk & Impact Assessment

Risk Level: low

  • Two-line change to namespace strings in package.json and server.json
  • No runtime impact — mcpName is only used by the MCP registry

Test Plan

  • mcp-publisher validate — passes

Manual Verification Steps

  1. After merge, wait for release-please to create a release PR
  2. Merge the release PR to publish to npm with updated mcpName
  3. Run mcp-publisher publish to register on the Official MCP Registry

🤖 Generated with Claude Code

The registry requires public org membership verification which
isn't resolving for the atriumn org. Use jeff-atriumn personal
namespace instead — still points to the same repo and npm package.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vercel
Copy link

vercel bot commented Feb 27, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tokencost Building Building Preview, Comment Feb 27, 2026 0:12am

Request Review

@jeff-atriumn jeff-atriumn merged commit 61bed6f into main Feb 27, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant